docs(api): describe new drop_tip() behavior introduced in PAPI 2.18
#15078
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ecormany
force-pushed
the
docs_release-2.18
branch
from
cdecc11 to
a55d47a
Compare
ecormany
force-pushed
the
docstring-drop-tip-alternating-2.18
branch
from
87ad535 to
3f37a9e
Compare
jbleon95
approved these changes
May 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Describe the new
apiLevel-gated behavior fordrop_tip()in Python API 2.18.Addresses RTC-448
Test Plan
Sandbox API ref entry
Changelog
Move ¶ about change in 2.15 down, and add another ¶ about 2.18.
Review requests
This is how it works, right?
Risk assessment
None, docstring only.